-
Notifications
You must be signed in to change notification settings - Fork 38.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated cherry pick of #39115 #39074 #39630
Automated cherry pick of #39115 #39074 #39630
Conversation
ac9bc5c
to
1328d03
Compare
Jenkins GCI GCE e2e failed for commit ac9bc5c2587c1c487e76271ad4957f5db9662050. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins kops AWS e2e failed for commit ac9bc5c2587c1c487e76271ad4957f5db9662050. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins CRI GCE Node e2e failed for commit ac9bc5c2587c1c487e76271ad4957f5db9662050. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins Kubemark GCE e2e failed for commit ac9bc5c2587c1c487e76271ad4957f5db9662050. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins GCE etcd3 e2e failed for commit ac9bc5c2587c1c487e76271ad4957f5db9662050. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
Jenkins unit/integration failed for commit ac9bc5c2587c1c487e76271ad4957f5db9662050. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
eh what's going on with @k8s-ci-robot ? |
Jenkins verification failed for commit ac9bc5c2587c1c487e76271ad4957f5db9662050. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/lgtm |
@krzyzacy I updated the PR once, I think these are previous test result. We can wait for the new result. |
ref for kubernetes/test-infra#1348 |
Both node e2e and cri node e2e passed. I think the PR works! |
Thanks for the fix @Random-Liu! |
Setting P0 priority since the issue this fixes is blocking merges of cherry picks to the 1.5 branch. |
@saad-ali Could you add the |
whoops.. looks like the bot needs a different label |
Added the wrong approved :) Fixed |
Jenkins GCE Node e2e failed for commit 1328d03. Full PR test history. The magic incantation to run this job again is Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
woooo.... why no output... |
@k8s-bot node e2e test this |
Submit queue is blocked. Merging this manually to unblock merges to 1.5 branch.
|
Commit found in the "release-1.5" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked. |
Cherry pick of #39115 #39074 on release-1.5.
#39115: Do not use sudo when untar node e2e tar ball.
#39074: Support set user with
--ssh-user
flag when running remote